Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v17-next #1349

Closed
wants to merge 17 commits into from
Closed

v17-next #1349

wants to merge 17 commits into from

Conversation

raineorshine
Copy link
Owner

@raineorshine raineorshine commented Nov 5, 2023 •
edited
Loading

v17 fell behind, so I rebased it on main and pushed it to v17-next. This should serve as the basis for the v17 release.

This was done to avoid force pushing v17.

@raineorshine
Copy link
Owner Author

A lot of upgrades were made, but I broke something along the way. I'll take a closer look soon.

@raineorshine raineorshine force-pushed the v17-next branch 2 times, most recently from 28940d6 to 1a9df94 Compare November 5, 2023 20:52
@raineorshine
Upgrade fp-and-or.
c91e206
@raineorshine
npm: Throw a proper error when no mock version is provided.
aa6cb24 
getPackageVersionProtected does catch any errors, but it rethrows them if they are not 404's.
@raineorshine
Copy link
Owner Author

Merged into #1345.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@raineorshine